Does "DocumentationExamples" means actual documentation in that sense (so we would ping Amy to double check) or functions more as code pattern for users (so maybe we could change the name to something more like "CodePatterns" or remove this subfolder compleately and have it under Examples/NetworkVariable/DoorExample"

It is a place to keep working versions of our documentation examples for two reasons:

• If you want to test an example (currently), you have to copy it, paste it into a file, setup a test specific to the example, and then verify the example works.
  • The initial thought was to use this for our testing and modification purposes.
• We could eventually move these into samples, which then we can include:
  • The script (or a section of the script) and then always (under the source) link to the sample or script.

Many of our examples are "too simplified" such that it can leave room for users to make assumptions which may or may not be correct... if we are very clear about the "usage pattern" then hopefully that will help provide users with a pattern that won't lead to issues down the road.

Hmm, during Unity Talks there was a talk from Oleksandr Kokoshyn about Making code examples in Unity docs testable which I guess is what we are trying to achieve here? (Talk is not yet available but I think will be this week)

[DOCS link]
[See N4E reference]

Yeah... trying to start preparing NGO to follow a similar pattern now so it makes it easier down the road.

What about merging this as it is for now and create task to update those in the same way

I could have used #3959 to add the door example script... next time I will make sure to do that.